Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Documentation on the --config flag when using init #287

Merged
merged 6 commits into from
Oct 7, 2024

Conversation

LatentDream
Copy link
Member

@LatentDream LatentDream commented Oct 4, 2024

@@ -88,6 +88,14 @@ Then, execute:
ploomber-cloud deploy
```

**Optional Configuration**:
You can use the `--config` flag with the `ploomber-cloud init --from-existing` command to specify a custom name for the configuration file instead of the default `ploomber-cloud.json`. When using this flag, only the file name will be considered, regardless of any specified path. For example:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a reference to this section

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Added 7d7b32d
✅ Fix Warning block rendering 7cc4de5

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not clear: ..and any specified path is ignored.. Also, I meant in this section you can add a link something like, `Refer to this section to learn more about switching configurations. You can look at other files to see how we link sections from the same file.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to be sure, is this what you had in mind ? b525cfd

  • Precise that --config can but use with a path. not just a name
  • Refer to the config section to know more about switching the config file


```sh
# create the config file in ploomber-cloud.dev.json
ploomber-cloud init --config ploomber-cloud.dev.json

# deploy using the dev config
ploomber-cloud deploy --config ploomber-cloud.dev.json
ploomber-cloud deploy --config ./config/ploomber-cloud.dev.json
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did we add ./config/..?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As an example of a path. We can leave it as it was

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
ploomber-cloud deploy --config ./config/ploomber-cloud.dev.json
ploomber-cloud deploy --config ploomber-cloud.dev.json

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fix: 39b8ba2

@edublancas edublancas merged commit 9adf7da into main Oct 7, 2024
1 check passed
@edublancas edublancas deleted the 143-easy-migration-from-ui-to-cli-config branch October 7, 2024 18:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants